Implements docs/superpowers/specs/2026-07-12-agentcore-onboarding-fix-design.md:

- config: delete the vestigial memory-ID env-var gate and both dead Config
  fields; backend resolution is now env > $BETTER_MEMORY_HOME/settings.json >
  sqlite via public resolve_storage_backend(); region single-sourced from
  agentcore.json (BETTER_MEMORY_AGENTCORE_REGION deleted); boto3 ImportError
  gains a better-memory[agentcore] install hint; AgentCoreConfigError messages
  gain remediation text
- mcp: dispatch wired — memory.observe/semantic_observe/record_use/
  retrieve_observations/credit/semantic CRUD route to AgentCoreBackend in
  agentcore mode via additive keyword-only remote param (sqlite branch
  verbatim); episode/retention tools hidden via supports_episodes; lazy
  session-id re-resolution in the backend
- hooks: session_close backend gate is settings-aware (env still wins, zero
  I/O on the sqlite fast path); session_bootstrap routes through
  build_backend in agentcore mode; boto3 hint mirrored
- cli: agentcore init activates by default (atomic merge-write of
  settings.json, --no-activate opt-out); honest next-steps output; status
  reports effective backend + source
- e2e: pin tests inverted per their FIXME contracts (dispatch-gap ->
  TestMcpDispatchWired with wire assertions, region split-brain ->
  TestRegionSingleSource convergence, idvar machinery deleted, anti-
  resurrection grep-pin added); new write_backend_settings helper
- NEW tests/e2e/test_agentcore_journey.py: 8-step full-flow journey on the
  shipped onboarding config (settings.json, zero env knobs) with per-step
  wire assertions and no-sqlite-leakage checks; live T3 journey additions
- tests/conftest.py: autouse BETTER_MEMORY_HOME isolation (unit tests must
  never read the developer's real settings.json)
- docs: truth-first sweep of README + website (activation flow, deleted env
  vars, corrected sqlite-traffic claim, init next-steps quoted from source)

Full suite: 1388 passed, 22 skipped. Pyright 0 errors. Ruff delta vs main: 0.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

…rs (Hive repair wave)

Live-AWS scout empirically mapped the record-plane dialect against a
throwaway memory pair (notes: aws_record_dialect.md); repairs per findings:

- storage/agentcore.py + cli smoke: BatchCreateMemoryRecords uses
  requestIdentifier+timestamp (memoryRecordId rejected by the real model);
  polarity filtering reworked to what ListMemoryRecords actually supports;
  semantic read path queries the exact write namespaces; BatchUpdate
  full-snapshot shape corrected for record_use/credit/ratings
- backend majors: session id re-resolved per operation (no process-lifetime
  freeze on a stale marker); promoted/general reflections fanned into
  retrieve() + session_bootstrap() (two-namespace merge, deduped)
- hooks majors: session marker written BEFORE backend wire calls (contract
  change — degraded first sessions now still bridge their session id; C2/C3
  pins updated, M2 mutation replaced accordingly); session_close closure
  actorId uses canonical project_name() instead of basename(cwd)
- payload parity: apply_session_ratings returns the sqlite shape, retrieve
  strips internal ranking keys, retrieve_observations key parity,
  session_bootstrap honors cwd
- fake endpoint now REJECTS what real AWS rejects (unknown record keys,
  unregistered metadata filter keys) so the hermetic tier cannot drift
- hygiene: settings read tolerates OSError; unit tests no longer read the
  developer's real settings.json; live-test Namespace fixes

Full suite: 1416 passed, 22 skipped. Pyright 0 errors.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

…e updates

- storage/agentcore.py: reflections fetch pages with nextToken under the
  real service's maxResults<=100 constraint (live ValidationException at
  120); list_events clamped
- fake endpoint enforces the cap so the hermetic tier pins it
- live tests: E4 polls retrieves with a bounded retry (record index lags
  ~60s per the dialect scout — writes are synchronous, the LIST index is
  not); E5 asserts the sqlite-parity ratings shape; E7 reads back the
  closure event under the canonical project actor (the actor-consistency
  fix moved it off basename(cwd))

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>